Skip to content

chore(sdk): regenerate for validation status and live-statement validation - #197

Merged
jfrench9 merged 1 commit into
mainfrom
chore/statement-validation-status
Aug 28, 2026
Merged

chore(sdk): regenerate for validation status and live-statement validation#197
jfrench9 merged 1 commit into
mainfrom
chore/statement-validation-status

Conversation

@jfrench9

Copy link
Copy Markdown
Member

Summary

Regenerated against robosystems bugfix/statement-validation-coverage (#1303, main + one commit):

  • ValidationCheckResponse.status / ValidationLite.statuspassed | failed | inconclusive; schema.graphql snapshot refreshed (ValidationCheck / InformationBlockValidation).
  • LiveFinancialStatementResponse.validation — guard-rail outcome for the rendered columns (new ValidationCheckResponse model on this client).

Also catches the generated tier up to main since the last regen (all live in API v1.11.6): resume_operation + OperationResumeRequest, nullable fact-grid total / average, description updates.

Generated tier only — the stable tier (facades, the six emit operations and their request models) is untouched. Client minor.

just test-all green (526 passed, 17 skipped; lint + typecheck clean).

…ation

Picks up robosystems #1303: `status` (passed | failed | inconclusive) on
ValidationCheckResponse / ValidationLite (REST + GraphQL schema snapshot)
and `validation` on LiveFinancialStatementResponse. Also catches the
generated tier up to main since the last regen: resume_operation, nullable
fact-grid total/average, description updates.
@jfrench9
jfrench9 merged commit 5cdb7e5 into main Aug 28, 2026
4 checks passed
@jfrench9
jfrench9 deleted the chore/statement-validation-status branch August 28, 2026 18:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant